Merge v2.67.0 into main - #1761

package.json (1)

121-136: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Several @babel/plugin-proposal-* packages left on old, now-deprecated versions.

While most @babel/* packages were bumped to 7.29.7, plugin-proposal-class-properties, plugin-proposal-export-namespace-from, plugin-proposal-json-strings, plugin-proposal-nullish-coalescing-operator, plugin-proposal-numeric-separator, and plugin-proposal-optional-chaining were left at older pins. These proposals were finalized into the ECMAScript standard and Babel has officially deprecated them in favor of @babel/plugin-transform-* equivalents (already effectively covered by @babel/preset-env). Consider removing these deprecated packages/plugins entirely rather than keeping them pinned.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` around lines 121 - 136, The dependency list still includes
deprecated proposal plugins, so update the Babel config in package.json by
removing the finalized `@babel/plugin-proposal-*` entries such as
`plugin-proposal-class-properties`, `plugin-proposal-export-namespace-from`,
`plugin-proposal-json-strings`, `plugin-proposal-nullish-coalescing-operator`,
`plugin-proposal-numeric-separator`, and `plugin-proposal-optional-chaining`,
and rely on the existing `@babel/preset-env`/transform plugins instead. If any
of these features are still required explicitly, switch to the corresponding
`@babel/plugin-transform-*` packages rather than keeping the proposal versions
pinned.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

.circleci/create-release-draft.js (1)

19-37: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

No top-level rejection handling or request timeouts on the GitHub API calls.

The async IIFE has no .catch(), so failures (network errors, malformed JSON, thrown Errors) surface only as an unhandled promise rejection rather than a clearly logged, intentional failure — relies on Node's default crash-on-unhandled-rejection behavior for the CI job to fail. The fetch calls also have no explicit timeout, so a stalled GitHub API request would hang until CircleCI's own job timeout kicks in.

🛡️ Proposed fix

-(async () => {
+(async () => {
   const res = await fetch(`${api}?per_page=100`, { headers });
   if (!res.ok) throw new Error(`Failed to list releases: ${res.status} ${await res.text()}`);
   ...
   console.log(`Created draft release for ${tag}.`);
-})();
+})().catch((err) => {
+  console.error(err.message || err);
+  process.exit(1);
+});

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.circleci/create-release-draft.js around lines 19 - 37, The async IIFE in
create-release-draft.js should explicitly handle failures instead of relying on
unhandled promise rejections, and the GitHub API requests need a timeout. Add a
top-level .catch() to the IIFE so errors from the fetch/json/throw paths are
logged clearly and cause a controlled non-zero exit, and wire an AbortController
(or equivalent timeout handling) into both fetch calls so stalled requests fail
fast rather than hanging the CI job.